An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi Apple team, App: DEADGRID Version: 2.0.1 App Apple ID: 6790152649 I'm reaching out in the hope that someone from the App Review team can take a look at my submission or advise whether there's an issue with it. My app has been in "Waiting for Review" for over a week and has not yet entered the "In Review" stage. I understand review times can vary, but this is significantly longer than what I've experienced previously. I've done my best to follow all App Store Review Guidelines and have provided complete review notes. As far as I'm aware, there isn't anything unusual about this submission that would explain the delay. Unfortunately, this update contains a fix for an issue currently affecting my users. While it's waiting to be reviewed, I'm seeing a decline in daily active users and user retention because I'm unable to release the fix. If someone from Apple is able to check whether my submission is simply waiting in the normal queue or if there's another issue preventing it from being reviewed, I would be very grateful. I'd also be interested to hear from other developers: Have you experienced similar review delays recently? Is there anything that can help move a submission forward when it's been waiting for this long? Are there any common reasons for an app to remain in "Waiting for Review" for more than a week? I appreciate the work of the App Review team and understand the volume of submissions you process every day. I'm mainly hoping someone can verify that my submission hasn't become stuck or overlooked. Thank you for your time. Afonso Quinaz

Hello, My app MGY Fit (Apple ID: 6793196121, iOS, version 1.0.0, build 11) was submitted for review on July 23, 2026 and has remained in "Waiting for Review" ever since. It has never moved to "In Review". There are no messages in the Resolution Center and I have not received any request for additional information. Export compliance, content rights, and advertising identifier questions were all answered at submission, and the Review Notes include demo account credentials and steps to reach the main flows. This is the first submission for this app and for my developer account, so I understand a longer wait is expected. I wanted to check whether the submission may have been routed in a way that needs attention, or whether this is simply current queue volume. Any guidance would be appreciated. Thank you.

hi,my app is still in review process since 3 days. is it normal? i have 4 apps on app store and they took maximum 1 day to be reviewed.

I have been waiting a week since I initially posted my app for review. since then there have been no emails, updates, or progress. I tried sending an email through the contact us page in App Store Connect with no response. I even tried calling and I sat on hold waiting for someone to pick up for 4 hours before I had to get off. Case ID: 20000128292512 what else can I do in order to get the ball rolling on this? I need to get it live soon

Hi all, I submitted an update for my app (VowFolio, bundle ID com.helgemeisal.vowfolio) for review almost a week ago, and it's still sitting in "Waiting for Review." It hasn't even moved to "In Review" yet. This is a minor update, just bug fixes and small improvements, so I wasn't expecting anything close to this long a wait. Typical turnaround for me has been 24 to 48 hours, so this is a significant outlier. No rejection, no request for more information, no message in Resolution Center. It's just sitting there. A few questions for the community: Has anyone else noticed longer queue times recently? Is there a recommended way to check on status beyond just waiting, or to nudge the review team without risking a rejection? At what point does it make sense to reach out to Apple Developer Support directly? Any insight from others who've hit similar delays would be appreciated. Thanks!

Hi everyone, I'm looking for advice on whether there is anything else I can do in this situation. Submission ID: 2270e15a-3c0a-4c56-84a1-a25abdc29622 I submitted version 2.0 of my app on July 19. Unfortunately, it remained in Waiting for Review for 10 days. Before submitting 2.0, I removed the legacy In-App Purchases from the live 1.8 version because I expected version 2.0 to be approved within the usual review timeframe. Version 2.0 introduces a new purchase model (subscriptions + lifetime), so I wanted to avoid users purchasing legacy products shortly before the migration. Unfortunately, the much longer review time meant that users of the current App Store version can no longer purchase or activate the Pro version, and I am now receiving support emails from customers asking why purchases are unavailable. I requested an expedited review, and the app entered review, but it was rejected due to two metadata issues: the Apple Standard Terms of Use (EULA) link was missing from the App Store description, and the submission still contained outdated 5.5-inch iPhone screenshots. The reviewer also wrote: "The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know. You do not need to resubmit your app for us to proceed." My intention was to accept that option and release version 2.0 immediately, addressing the metadata issues in the following update. Unfortunately, before I realized this, I had already corrected the metadata and clicked Submit for Review again. That caused the Reply option to disappear, so I could no longer tell the App Review team that I wanted to proceed with the current submission. The app is now back in Waiting for Review, and I'm trying to understand whether my resubmission unintentionally reset the review process or whether the original expedited review request is still being honored. Has anyone experienced something similar? Is there any way to continue the original review, or am I now back at the end of the review queue? If anyone from the App Review team happens to see this, I would greatly appreciate any guidance. Releasing version 2.0 would immediately resolve the issue my customers are currently experiencing with purchasing and activating the Pro version. Thank you very much!

Dear App Review Team, I'm following up on our submission with App ID: 6786827398, submitted on July 15, 2026. The submission was first reviewed on July 27, after an exceptionally long 12 days of silence. During that time, we have received no status update, no rejection, no metadata feedback, and no communication of any kind. Then the app was automatically rejected. We asked for clarity on the rejection and received no response. In the absence of any communication, we made several updates and submitted another version on July 31st. It is now August 7. The app is once again waiting for review with no communication from App Review whatsoever. We have also reached out via Apple Developer Support regarding this issue several times and have not received a response from that channel either. These delays are significantly outside the typical review window Apple publishes. Apple specifically says "90% of submissions are reviewed in less than 24 hours". We need clarity on the following: The current status of the submission and the reason it is not being reviewed by the App Review team. A concrete timeline for when the review will begin or conclude. Confirmation of whether any internal flag, hold, or routing issue is affecting this build. The submission is complete and ready for review on our end. We respectfully ask for a prompt response and resolution. Thank you.

Hello, We are preparing to submit our banking application to the App Store and would appreciate some guidance regarding our review and release process. Due to our organization's deployment process, we plan to submit a production build that is configured to connect to our UAT backend during App Review. This will allow the App Review team to test all functionality using dedicated test credentials. After the app is approved, we intend to submit another build that is identical in functionality but configured to connect to our production backend before releasing the app to customers. A few questions: Is this approach acceptable under the App Store Review Guidelines? Has anyone successfully followed a similar workflow for enterprise or banking applications? Since the second submission would primarily change the backend environment (UAT → Production), is it generally reviewed as a normal update, or is there anything we should be aware of? Our planned public launch is 7 September 2026. Is there any recommended approach to help ensure the production update is reviewed before the launch date? We understand review times cannot be guaranteed. Due to our bank's security policy, our UAT environment is available only from 10:00 AM to 10:00 PM IST (Indian Standard Time). Is mentioning this in the App Review Notes sufficient, or is there a better way to communicate these testing hours to the App Review team? The app will be fully functional during review, and we will provide complete test credentials and any other information required by the App Review team. We appreciate any guidance or best practices from Apple or developers who have gone through a similar review process. Thank you!

Hello, My QueenBoard app update was submitted more than four days ago and is still awaiting a review decision. There are no messages in the Resolution Center and no requests for additional information. Details: App: QueenBoard - Logic Puzzle Games Apple ID: 6774414102 Platform: iOS Version: 1.2.4 Build: 26 Submitted: July 26, 2026 at 6:40 PM Current status: In Review Submission ID: 1d5aa681-6804-4aab-9a2c-50c411d856de This is an update to an existing app that has already been approved and published. All required app information has been completed, and I have not received any notice indicating that action is required from me. Could someone confirm whether the review is proceeding normally or whether there is anything I need to provide? Thank you for your help. Best regards, Tim Nguyen

Hello Apple Developer Community, I'm reaching out regarding an urgent matter that requires immediate attention from the App Review team. SITUATION: Our production mutual TLS (mTLS) security certificate expires on August 15, 2026 — only 11 days away. We have submitted version 4.3.1 of our iOS app (Mibanco) which includes the mandatory certificate renewal implementation. WHAT WE'VE DONE: ✅ Implemented dual-certificate coexistence for safe rotation ✅ Tested v4.3.0 thoroughly in TestFlight production ✅ Validated mTLS authentication without errors ✅ Confirmed backward compatibility with legacy systems ✅ Zero user-facing impact OUR REQUEST: We need HIGH PRIORITY review and approval of v4.3.1 before August 15, 2026. This is a critical security infrastructure renewal, not a feature release. Submission ID: b148b754-1abe-451e-b4ac-ad285abbc6da Thank you for your urgent attention to this time-sensitive security matter. Best regards, Alberto Adrian Quineche Poma Engineer Mibanco

Hi everyone, I'm wondering if anyone from Apple or other developers has seen a similar situation. My app is currently in Waiting for Review, and there has been no movement for several days. A bit of context: This is the first release of my app. My initial submission was rejected due to a design-related issue, which I addressed. I submitted a new build on August 1 (IST), and it has remained in Waiting for Review ever since. I have already submitted an Expedited Review Request, but I haven't received a response yet. I understand review times can vary, but I'm concerned because I've seen many other apps submitted around the same time already move into review or get approved. Is there currently a backlog in App Review, or is there anything else I should do besides continuing to wait? Any guidance from Apple or developers who have experienced something similar would be greatly appreciated. Thank you!

It has been a week since we submitted our app update, and the app is still in Pending Review. We previously contacted Apple Support regarding this issue and received a case ID via email. However, we have not received any response or update on the status of our case. We also could not find any place to track the case using the case ID that was provided.

We build and operate a management platform for fitness studios — bookings, memberships, payments, class schedules. We're planning the mobile side now and want to get the App Store model right before we build the release pipeline rather than after. What we have One codebase, which we write and maintain. It ships in two configurations from the same source: A marketplace app — every studio on the platform, searchable, with a picker. One binary, one listing, our brand. A per-studio configuration of that same app — identical functionality, with that studio's name, logo and colour palette, pointed at that studio's data. Studios ask for the second because they want their own presence in the store. Each one is a real business: real class schedules, real bookings, real payments taken by that studio, real members using it weekly. What I'm unsure about 4.2.6 Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. I can read that two ways and I'd rather ask than guess: (a) It targets app-builder products, where the customer assembles an app themselves from a toolkit and the vendor's product is app generation. We aren't that — customers never touch a build tool, and the app is our own software that we develop, update and support. (b) It applies to any per-client build regardless, in which case each studio needs its own Apple Developer account and submits with us added to their team. Questions Which reading is right for a SaaS product where the vendor writes and operates the app, and the client supplies business data rather than an app? If per-studio builds can be published under our own developer account, is there anything specific you'd want to see in the submission or the App Review notes to make that clear? Separately from 4.2.6 — what makes per-client apps sufficiently distinct under 4.3? This is the part I'm least sure about, because it reads as a judgement about the pattern across many apps rather than about any one of them, and I'd rather design real differentiation in now than discover the line at app number fifty. Is "same functionality, different business, own branding, own data" enough, or is more expected? Does the aggregated / picker option in 4.2.6 change the answer if we ship it alongside? We're building the marketplace app regardless, so both would exist. Happy to give more detail on the product. I'd rather build the right pipeline once than appeal a rejection later.

I've been unable to resubmit my app for review for several days, and now App Store Connect can't even load my subscription data. Submission: "Add for Review" / "Resubmit to App Review" on my app version (iOS 1.0) or subscriptions returns "An unexpected error was encountered when submitting for review. If the issue persists please contact us." The app version shows "Removed" and the subscriptions (Monthly, Yearly) show "Developer Rejected," and I can't add them back. Subscriptions page: Distribution → Subscriptions now shows "An error has occurred. Try again later." under both Subscription Groups and Billing Grace Period, so the page can't load my subscription data at all. Diagnostic detail: builds 7 and 9 both fail the submission error (both "Complete" in TestFlight, no Missing Compliance), while an earlier build (5) added for review fine — so submissions work in general; it's specific to the current submission/subscription state. Already tried: fresh incognito + a different browser, removing and re-adding items, uploading new builds, waiting several days. I've emailed Developer Support (no reply yet) and can share the submission ID and app ID with an Apple staffer. Has anyone hit this, or can an Apple staffer help get it unstuck? Thank you.

Hi all, I’m building a sandboxed macOS app that, among other things, lets the user create and associate an Apple Note with a calendar meeting. The user explicitly initiates the action. The app uses AppleScript to create the note, obtain its identifier, and open it in Notes. Notes only declares the com.apple.Notes.openlocation scripting access group. Note creation is not covered, so com.apple.security.scripting-targets does not appear sufficient. The working implementation requires: com.apple.security.automation.apple-events com.apple.security.temporary-exception.apple-events for com.apple.Notes NSAppleEventsUsageDescription Has anyone successfully shipped a Mac App Store app using this temporary exception to control the built-in Notes app? Is this potentially acceptable with a clear entitlement explanation and Feedback Assistant report, or should I assume that note creation through AppleScript cannot be included in a Mac App Store build? Is there another supported API that can create an Apple Note and return an identifier or openable URL for it?

Hello Apple Developer Community, I'm reaching out regarding an urgent matter that requires immediate attention from the App Review team. SITUATION: Our production mutual TLS (mTLS) security certificate expires on August 15, 2026 — only 11 days away. We have submitted version 4.3.1 of our iOS app (Mibanco) which includes the mandatory certificate renewal implementation. WHAT WE'VE DONE: ✅ Implemented dual-certificate coexistence for safe rotation ✅ Tested v4.3.1 thoroughly in TestFlight production ✅ Validated mTLS authentication without errors ✅ Confirmed backward compatibility with legacy systems ✅ Zero user-facing impact OUR REQUEST: We need HIGH PRIORITY review and approval of v4.3.1 before August 15, 2026. This is a critical security infrastructure renewal, not a feature release. Submission ID: b148b754-1abe-451e-b4ac-ad285abbc6da Thank you for your urgent attention to this time-sensitive security matter. Best regards, Alberto Adrian Quineche Poma Engineer Mibanco

Hi, Our macOS app has been in Waiting for Review since Jul 24, 2026 with no status change. Platform: macOS Version: 1.0 (1) App Apple ID: 6794145764 Submission ID: 5d04a433-b67d-4801-8578-b1ccc3f22d34 Support case: 20000126982226 We also requested an expedited review and contacted support more than once; no reply so far. Our earlier iOS submission was reviewed within a few days. This macOS one hasn’t moved at all. Is anyone else seeing long macOS “Waiting for Review” times right now? Any advice on getting this unstuck, or can someone from App Review take a look? Thanks.

App name: Bromure Client App id: 6793724385 Submission id: 33c98717-eb8d-4b2d-867e-0cc0bf2ef89d My app has been suck in the state of "in review" since 7/31. The credentials provided to test the app have never been used by the Apple team. I emailed support -- never received any answer. Does anyone have any idea on what could be happening? I initially submitted the app on 7/27. How much longer should I expect to wait?

My app was rejected July 16 under Guideline 2.1 (Information Needed) with four questions about the Clinical Health Records API. I replied in full the same day in the Resolution Center, and followed up in that thread on July 22. It has now been 12 days with no response from App Review. I have also contacted Developer Support (case 102942988807), which replied twice but could not provide status on the submission. I have not clicked Resubmit, since Apple's message asked me to reply, and I understand resubmitting closes the correspondence thread. Is there anything further I should be doing, or is a reply alone sufficient to return the submission to the review queue? Submission ID: bc855e56-3ef8-482d-96b0-4380d3fc4a68

Hello, My app Air Finder - My Device Tracker (Apple ID: 1490211589) seems to be stuck in the App Review process and I'd like to check if something might be wrong with my submission. Timeline: Submission for review: Jul 30, 2026 Current status: Waiting for Review Waiting time: 7 days as of Aug 6, 2026 My app reviews are typically approved within 1-2 business days, so I suppose this delay seems to be unusual. Please help review this submission as soon as possible! I have a timeline for publishing app version that cannot be delayed for this long. Any guidance would be very appreciated. Thank you in advance!